Release Notes for the Axiell Collections Software
In this section you will find release notes for the Axiell Collection Software (broadly speaking the user interface and all of the functionality and tools it provides for working with your collections data).
Tip: Release notes for the Axiell Collections Model Application (the data management heart of Axiell Collections) can be found here. An explanation of the difference between the Axiell Collections Software and the Model Application can be found here.

As development of Adlib for Windows has ceased, functions introduced in Axiell Collections version 1.11 onwards are not supported by Adlib for Windows.
Applications using Collections-only functionality should never be opened in Adlib for Windows as the system may become unreliable.

IMPORTANT: Upgrading to Axiell Collections 2.0 in systems running Model Application 5.1 and earlier
It is possible that exhibit.inf
is missing a tag Tn
of the Temporary
data type. Before installing Axiell Collections 2.0 we recommend that this tag is added (and your IIS app pool is then recycled). Collections 2.0 demands higher integrity of the application structure files: if your application is using a non-Full text
indexed database, the missing tag will cause an internal server error when a search is started in the Exhibitions data source; if your application is using a Full text
indexed database, the Exhibition data source will be accessible but the Exhibition title (words) access point will not be available.
Requirements
Microsoft .NET Framework Runtime version 4.8 must be installed on the IIS server running Collections (after which the server needs to be rebooted).
Full details about technical requirements and minimum specifications can be found here.

Release Date: 28 February 2025

Application Administrators should review the Axiell Designer Release Notes for recent changes that impact Collections.


Axiell Intelligence is an optional feature designed to enrich your Collections data by leveraging AI to identify entities (people, places, dates, and so on) in your unstructured content and write-back structured keyword metadata linked to authority records and Wikidata.
The core concepts of Axiell Intelligence are Entity Extraction (also known as Named Entity Recognition) and Entity Linking. The first identifies entities within unstructured text in nominated fields, and classifies them into predefined categories such as individuals (people’s names), organizations (names of companies, institutions, or groups), locations, dates, times, and more. Structured metadata in the form of keywords (names, terms, etc.) is then written back to the source records, linked to authority Authority data sources are used for vocabulary control and they manage the many names and terms referenced by records in almost every other data source. The purpose of a controlled vocabulary is to ensure consistent use of names and terms throughout your records and this is achieved by specifying that a name or term is preferred; then when a non-preferred version of a name or term is selected in a Linked field drop list, it is automatically replaced with the preferred name or term. records in Persons and institutions and the Thesaurus (created on-the-fly if necessary) and to Wikidata.
Axiell Intelligence's AI is able to process data faster and more efficiently than we can, while enabling human oversight to ensure an ideal combination of machine and human intelligence. The end result is enriched data with interlinked records, providing improved context for staff, researchers, and the public.
For the moment, Axiell Intelligence is only available for English language content.
You will find full details about Axiell Intelligence here.
Dialogue box improvements

A Settings button has been added to the Find data for the field box, enabling users to customize which columns display and in what order (similar to Result set View):
In the Settings dialogue it is possible, amongst other things, to add / remove fields (columns) and to reorder them:
Details about working with the Settings dialogue can be found here.
As can be seen above, it is possible to include thumbnails in the Find data for the field box by including the image or media reference field in the Find data for the field box. When only one thumbnail displays, this is the first or preferred image linked to a record. More thumbnails can be shown by specifying the maximum number of thumbnails to display in the event that more than one image is linked to a record.

The Record History Reports function is an optional feature that allows suitably authorized users (those with the $ADMIN
role) to list records changed within a period, with the old and new values displayed per field. Full details about the function can be found here.
A number of improvements have been made for the Collections 2.0 release:
- All labels for column names and buttons now display in the current interface language.
- A Field name column has been added to hold the system name of fields in the current interface language:
Tip: All column labels and data are exported with the Export to CSV option.
- The Record History Reports window lists records changed within a specific period; each row identifies a change to a record and the first column includes one of three icons to indicate whether a value was added (
), deleted (
) or modified (
).
The first column is now labelled Type (previously it had no label); placing the cursor over the column label pops up a tooltip that describes the icons:
- Previously, when a value in a Linked field
A type of field used to link one record to another. A Linked field is a drop list of values (records that the field can link to). When a link is made, the field stores a reference to the linked record (a linkref). was changed, only the old record number and the new record number in the link reference fields were shown in the Record History Reports window. Now the link reference values are replaced with the value of the linked term (a person's name for instance). The Tag and Field name columns now show the tag and name for the Linked field (instead of its link reference field).
Note: As a consequence of this change, sorting is no longer possible on the New data and Old data columns. If it is necessary to sort on the data columns, it is possible to export the list to a CSV and use Excel for sorting.
Import / Export

The title bar in the Import dialogue now includes the name of the target data source, making it clear which data source you importing data into. Previously it only stated Import:
Details about importing data can be found here.

When importing data into Collections you will find two additional options, AdlibXML (grouped) and AdlibXML (unstructured), in the Import box:
A Style Sheet drop list will display when either of the Adlib XML formats is selected, but it will only be populated if Application Administrators have set up a custom import job. A custom import job is used to convert a non-Adlib XML exchange file (one that is MarcXML or LIDO, for instance) to AdlibXML in order that it can then be imported into Collections. If the Style Sheet drop list is empty, simply ignore it (your exchange file already contains structured or grouped AdlibXML); if, for example, the import data file contains MarcXML and an appropriate style sheet has been made available, you would select it from the Style sheet drop list:
Tip: An XSLT style sheet is provided for import of object data from EODEM Exhibition Object Data Exchange Model exchange files are designed to simplify and streamline the process of sharing information about exhibition and loan objects between different museum collections management systems. exchange files. The registration of third-party objects for loans and exhibitions is greatly simplified when participating parties support the generation and import of data via the EODEM.
Continue to set up the import as usual by specifying the file containing the import data and confirming that the other options in the Import box are correct (details about how to import data can be found here). Note that it is not possible to specify a subset of fields to import when importing Adlib XML (step 6 in How to import data).
Tip: Application Administrators will find details about setting up custom import jobs to produce unstructured or grouped AdlibXML for import into Axiell Collections in the Axiell Designer Help.

When exporting data it is now possible to use custom XSLT formats to transform Collections' native (unstructured or grouped) record XML to another format (e.g. HTML).
When set up for a data source by an Application Administrator an Xslt option is added to the Format drop list in the Export box; when selected, a Style Sheet drop list will display to the right, from which the required export format style sheet is selected:
Tip: An XSLT style sheet is provided for export of object data to EODEM Exhibition Object Data Exchange Model exchange files are designed to simplify and streamline the process of sharing information about exhibition and loan objects between different museum collections management systems. exchange files. The registration of third-party objects for loans and exhibitions is greatly simplified when participating parties support the generation and import of data via the EODEM.
Axiell Collections' predecessor, Adlib for Windows, supported custom export formats, and any custom XSLT export formats that were migrated from Adlib to Collections will now be available in Collections following installing of Collections version 2.0.
Tip: Application Administrators will find details about configuring this functionality in the Axiell Designer Help.
Search

With a Filter, users can define a subset of records in a data source The management of a collection can involve a vast amount of information about objects / items / books, people and organizations, events, administration and more. This information is stored as records in data sources. Each data source stores a specific type of information: details about collection items, people, events, loans, and so on. and limit all their searches to this record set while the filter is active. A curator of ceramics, for example, might only be interested in Object catalogue records where:
- Management status = internal
-AND-
- Object category = ceramics
By specifying a filter with these conditions, any search by the curator in the Object catalogue will be restricted to the subset of records defined by these conditions, as long as the filter is active (full details here).
A filter icon displays in the Title bar when a Filter is active:
The query that defines the Filter is shown as a tooltip for the filter icon, and it is displayed on the Standard and Advanced tabs of the Search box. Here we see a Filter query on the Advanced search tab in Collections version 1.19:
As we see, field tags are used and, perhaps less obviously, the neutral value INTERNAL is used for the enumerative field Read-only drop lists; their values are added and translated by Application Administrators in the Collections administration tool, Axiell Designer: users can select a value in an enumerative field, but cannot add or translate a value., e.g. Management status (
ms
) rather than the display value internal. With enumerative fields, the neutral value (a language independent value stored in the database) can be more cryptic than the display value (the value that displays in the User Interface).
Now, the more user-friendly system field name is used instead of a field tag, and the display value rather than neutral value is used for enumerative fields. For example:
Here we see the Standard tab of the Search box:
And here, the Advanced tab of the Search box:
Note: If there is no field name defined in the current interface language, the field tag will be shown.
As we see above, system field name can include an underscore (they can also include dots). Application Administrators are able to specify a more user-friendly label (without underscores, for example) for the field name as a method text in the field definition in Axiell Designer A tool for designing, creating, customizing and managing Axiell Collections applications and databases, broadly speaking, the Axiell Collections Model Application. As well as managing databases, including user access and permissions, Designer is used for such tasks as translating field labels, tooltips, values in drop lists, etc.. When displaying the Filter query, a method text in the current interface language has priority over the system field name.
For example, a Filter query might be defined for the Level (record_type) field as:
Application Administrators could add a more user-friendly method text to the definition of the record_type field so that Level is displayed instead of record_type:

When Full text indexing has been implemented in a database, an equals search in a non-unique Text (term) indexed field The entire value in the field is indexed as a single value, including spaces and punctuation. When searching a text (term) field, your search value must exactly match the entire contents of the field. will not only match the value you are looking for but also values that differ in their use of punctuation. For example, a search for:
AB-12345
will return AB-12345
, ab12345
and aB123.45
.
Note: An equals search is case-insensitive.
The new exact operator, which is available in an Advanced search, only returns records with an exact match in terms of case and punctuation. For example:
alternative_number exact "AB-12345"
will only match AB-12345
.
An equals search in a unique Text (term) indexed field such as object_number is already punctuation-sensitive; an exact search ensures the match is also case-sensitive.
Note: The exact operator can also be used in READ Facs_name WHERE searches in adapl.
More details about indexing can be found here.

The introduction of the Period
field type1 made it possible to save and to search for date periods as a natural language value, such as 12th century, Spring 2023
, and so on.
Tip: Details about the Period field type (including a definition of the basic elements used to describe a period, and valid formats) can be found here.
When adding a value to a Period type field, and when specifying a search value, we use the natural language version of a period; while such fields display the natural language version of a period, the indexed (searchable) value is stored in the database as an ISO start and end date range (i.e. a numerical value). For example:
Period entered by a user |
Indexed value |
---|---|
12th century |
|
Spring 2022 |
|
late 2018 |
|
Early 19th Century - 2022 |
|
1950s |
|
Performing an equals
search on a Period type field such as:
Production period = "spring 2023"
will find records in which the field contains dates falling within the spring of 2023; performing a wider search on the specified period was not possible as it is only possible to search for a single period, not period ranges.
This changes in Collections 2.0 with the introduction of the overlaps
operator. More descriptive labels have also been provided for the various Relational operators:
Operator |
Details |
|||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Perform a wider search on the specified period by returning any records in which a date intersects with (overlaps) the search date. For example:
will return records with periods such as ![]() It is important to understand that Production period overlaps 2000 will not return records earlier than the year 2000 for instance. It is more accurate to describe an In the example above, the date range of Production period overlaps 2000 any period that intersects this range is considered to overlap, and a record with an overlapping period in the search field will be returned:
Note: This operator is also available for Advanced searches (and WebAPI requests), and it is the default operator for Period type access points |
|||||||||||||||||||||
within |
Used for A search of: Production period within "circa 2000" will return records with periods such as Tip: |
|||||||||||||||||||||
after |
Return records where the value in the search field is later than the search period. Used for |
|||||||||||||||||||||
after including |
Return records where the value in the search field is later than or the same as the search period. Used for |
|||||||||||||||||||||
before |
Return records where the value in the search field is earlier than the search period. Used for |
|||||||||||||||||||||
before including |
Return records where the value in the search field is earlier or the same as the search period. Used for |
|||||||||||||||||||||
is not empty |
Return records where the search field contains a value. Used for |
|||||||||||||||||||||
is empty |
Return records where the search field is empty. Used for |
Notes
- Search values with spaces or hyphens must be enclosed in quotes in an Advanced search; in WebAPI requests use the URL encoded version of a quote (
%27
for single quote), e.g.:wwwopac.ashx?database=collect&search=period%20within%20%272000-2002%27
- It is possible to use dates in the current interface language / region format.
Application Administrators will find details about implementing the Period
data type in the Axiell Designer Help.
Sort / Sorting

A change to how occurrences If a field in the current record can have more than one value, we add an occurrence of the field for each value (e.g. a book can have multiple authors so we add an occurrence of the author.name (au) field for each author). An occurrence can be a member of a group of fields, and adding an occurrence of the field adds all members of the group at once. are sorted in Collections 2.0 sees a significant improvement in performance.
A date field occurrence, for example, may be set to sort Descending; when a new occurrence of the field is entered and the record is saved, the occurrences are sorted and the most recent date is first. Previously, every sorted occurrence in a record was sorted automatically when the record was saved, even if there had been no change to the content of the field.
Now, sorting only occurs when a record is saved if the field contents have changed, resulting in a significant performance boost, especially where there are numerous sorted occurrences with many values.
Other

Previously, a Download or Upload button displayed to the right of email fields when editing records:
Email fields have an Application data type, which by default display the buttons (details in the Axiell Designer Help). The button no longer displays. In Display mode, email addresses are underlined and can be clicked to open your default email application to compose an email to the destination address:

Application Administrators are now able to specify a start and end point for an audio or video file; when Play is pressed in Media viewer the specified fragment of the media is played by default (although the entire file is available and can be played by manually dragging the slider in the media player):
There are various ways this feature can be implemented and Application Administrators will find details about configuring this functionality in the Axiell Designer Help. One approach is to link the Multimedia documentation record for an audio or video file to a Catalogue record and specify a start and end point for the linked media in the Catalogue record; in this way, sections of a media file could be specified and described in their own Catalogue record.
Tip: The start and end time must be specified in seconds (120 seconds for a start point of 2 minutes for example).

It is possible to view your Collections data in predefined reports, and to print these reports. Reporting and printing use the same templates (Microsoft Word templates, Excel templates or XSLT style sheets for example) to lay out and style your data; the main difference between reporting and printing is that reporting displays your record data on-screen, and printing is obviously intended to output your data to a printer.
Printing record data in Collections prior to version 1.18 involves selecting a template from the Output formats box, opening the associated third-party application (MS Word, MS Excel or web browser), and then printing the formatted data from the open application.
From Collections version 1.18 an option was added to print the result of an Output format directly to a printer, rather than first opening the third party application. When available, a Print button is added to the Output formats box:
Users select an output format from the list and then select Print to display a Select printer dialogue from which a printer is chosen:
Application Administrators will find details about configuring this option in the Axiell Designer Help.
Note: Note that this option is currently only available for local implementations of Collections and not the hosted implementation of Collections.
Collections version 2.0 extends this option by allowing Application Administrators to associate one or more printers with a particular output format, ensuring that users can only select an appropriate printer for the chosen output format (a label printer for printing labels, for instance). As before, a user selects a template from the Output formats box and clicks Print to display the Select printer dialogue, which now only lists one or more printers appropriate for this output format.
Tip: Application Administrators will find details about configuring this functionality in the Axiell Designer Help.

The background images used for the Collections Login page are stored in the ..\Content\Backgrounds\Login
folder of a Collections installation.
It is now possible to use your own images for the Collections Login page.
Application Administrators (with access to the Collections installation directory) need to create a Custom
folder:
..\Content\Backgrounds\Custom
in which to hold the custom background images (either .jpg
or .png
).
When Collections loads, the Custom
folder is checked first and any images stored there will display; if the Custom
folder does not exist or it contains no images, the images in the Login
folder are used.
Note: Do not replace the images in the ..\Content\Backgrounds\Login
folder as the images in this folder may be overwritten when Collections is updated.

When you select a term from an external thesaurus in a Linked field A type of field used to link one record to another. A Linked field is a drop list of values (records that the field can link to). When a link is made, the field stores a reference to the linked record (a linkref)., Collections now checks all unique indexes in the local thesaurus for a match with data from the external term record. If a match is found, the link will be made to the existing local thesaurus record; in other words, the external record will not be derived and a duplicate record will not be added to your local thesaurus.
Note: There is no notification when this happens.
As a result, Application Administrators should check which fields in the local thesaurus have a unique index if their system is also using an external thesaurus. If, for example, the Term field is uniquely indexed, it will not be possible to derive the same term from an external thesaurus even if the metadata is different; on the other hand, if a URI field (referencing a Linked Open Data term) has a unique index, it would be possible to derive the same term as long as the duplicate(s) in your local thesaurus do not have the same URI.

The Result set View toolbar includes a drop list of options for marking of records, including mark all / unmark all, drop marked records, etc. (details here). Marking / unmarking of all currently listed records can now also be achieved by clicking a checkbox in the column header row in Result set View:

Jira Issue # |
Brief description |
---|---|
CV1-6671 |
A search on a hierarchical indexed link returned error Invalid column name 'priref'. |
CV1-6666 |
In the Acquisition items data source, a Standard search on Acquisition reference number returned an Invalid column name 'priref'.” error. |
CV1-6635 |
Searching on reversely indexed Linked fields |
CV1-6631 |
In some circumstances an inline report could return an error 500 (Internal Server Error). |
CV1-6620 |
If on login a list of applications to choose from was shown, it was no longer sorted alphabetically. |
CV1-6617 |
If Result set View was very narrow, the Tasks list would be partially hidden behind the Main menu on the left. |
CV1-6612 |
Multilingual fields set up to use an external thesaurus could not derive data from that external thesaurus. The fix makes sure that terms are now added to the record with the current data language. This also means you can add the same term more than once if you change the data language. |
CV1-6600 |
If no link screen had been set for a Linked field, the list of found terms in the Find data for the field box remained empty. |
CV1-6587 |
When a field reversely linked to a Full text indexed field in another database table, multiple copied occurrences |
CV1-6572 |
An unresolved link remained when deleting a narrower record which was referenced multiple times in a broader record. |
CV1-6570 |
Saving a Thesaurus record after removing an occurrence of the domain |
CV1-6547 |
Images retrieved from BLOB storage (via a URL with File system as its retrieval type) and printed to a Word template were no longer scaled to fit the page or table cell. |
CV1-6546 |
When searching, an Invalid object name 'people_name' error could occur on a reversely indexed link when Full text indexing was used. |
CV1-6526 |
Using the Bulk create method to create multiple records, could result in a circular reference error while no actual circular references were being created. |
CV1-6519 |
The Bulk create method didn't resolve indexed linked broader-narrower relationships. |
CV1-6493 |
A Standard search on object number and priref |
CV1-6492 |
Related records View didn't display properly if the relevant database table definition didn't have datasets defined. |
CV1-6468 |
|
CV1-6464 |
Saving a new Saved search could be very slow. |
CV1-6461 |
Specific searches resulted in an invalid object name 'CTE_2' error. |
CV1-6457 |
Filtering the values in an enumerated |
CV1-6432 |
An error Could not load file or assembly 'System.Text.Json' was generated when executing a specific task. |
CV1-6430 |
Collections would hang when accessing an Object record linked to an acquisition which contained a very large number of links. |
CV1-6417 |
All multilingual Thesaurus values (if they matched the search key) would display in the Find data for the field box, regardless of the current data language. |
CV1-6411 |
An Object reference not set to an instance of an object error appeared when using Simple search. |
CV1-6410 |
Result set View sorting on the linked request.number field didn't work. |
CV1-6405 |
Search didn't get the right hits and the Full text table was not updated correctly when moving a Thesaurus term value into the term.code field. |
CV1-6402 |
In Edit mode |
CV1-6398 |
The Collections file cache for chunks from uploaded images or documents was never cleared after successful upload and storage. |
CV1-6394 |
Data in enumerative fields |
CV1-6383 |
Under specific circumstances, images were not printed to Excel Output formats |
CV1-6381 |
Sorting on an ISO date field didn't work if the field was set to inherit |
CV1-6376 |
Using operator AND in a search combining two wildcards returned the result of a search using OR. |
CV1-6375 |
Advanced search <fieldname> = '' or <fieldname> = "" did not select records where this field is empty, but selected all records instead. |
CV1-6374 |
When you added a use relation to a Persons and institutions or Thesaurus record all previous references to the name / term should have been updated to the new value in the use field, but when you had indexed link hierarchies like in collect.inf on tags bt/nt this was not properly handled and was dropping the bt/nt relations. This only happened when processing the feedback links when changing use/used-for in Persons and institutions or Thesaurus records. |
CV1-6371 |
If an index incorrectly contained a reference to a record which didn't exist, this would result in a blank screen without error message when searching. |
CV1-6366 |
For an OR combined search on a merged-in field and a Linked field from the same database table, the order of the two fields in the search statement mattered: in the wrong order, an Incorrect syntax near ')' error was generated. |
CV1-6360 |
In Word Template output, the first occurrence of a grouped repeated |
CV1-6359 |
In adapl, a |
CV1-6342 |
Selecting terms from the Find data for the field box didn't work for Linked fields with a variable domain |
CV1-6341 |
In German, copying a numeric value with two zeros after the comma (decimal separator) and pasting it again, removed the decimal separator (adding two zeros to the value). |
CV1-6340 |
There was an Object reference not set to an instance of the Object error when linking a specific object in Incoming loans in a specific environment. |
CV1-6338 |
An Initial value format property for URI fields did not work when the URI type property was set to |
CV1-6337 |
Icons in the Top toolbar and View context menus no longer showed the difference between their active and inactive state. |
CV1-6334 |
All Views could be closed, which meant that on the next search the user would see no search result. With the fix, now at least one view has to remain open. |
CV1-6333 |
Certain CSV imports could cause data loss. |
CV1-6321 |
A Word template with a header produced an error when printing directly to PDF. |
CV1-6293 |
A change in an occurrence sort order was sometimes not saved. |
CV1-6282 |
Resolving of a retrieval link with the |
CV1-6269 |
The list of found terms in the Find data for the field box was not refreshed when switching the Show candidate terms or Show only <domain> option on or off. |
CV1-6263 |
When a multilingual Linked field was shown as an enumerative |
CV1-6251 |
A language-specific search on a non-indexed field did not work correctly in multilingual applications. |
CV1-6226 |
For some records with images, thumbnails were not displayed in Result set View. |
CV1-6222 |
Access point searching on a merged-in multilingual field left the Find data for the field box empty. |
CV1-6208 |
For some access points |
CV1-6199 |
In a particular set up, the feedback link mechanism didn't work properly for meta data databases, causing preferred term substitution not to take place. |
CV1-6186 |
The Calendar widget was not fully visible after clicking on the Calendar icon for a date field in Record History Reports. |
CV1-6184 |
The Equivalent operator did not retrieve the expected records. |
CV1-6124 |
In output generated from Word templates, spaces between different field values on the same line disappeared. |
CV1-6116 |
A Simple search for data in alpha-numerical fields did not find matching records. |
CV1-6109 |
It was not possible to use a Linked field as the Update field for a Collections import. |
CV1-6103 |
When Collections got help texts from the Contextual Help application 1.0 it did not differentiate between upper and lower case letters, so the same help text was shown for two identical help keys in which the tags only differed in the use of capitals. |
CV1-6096 |
Related records View did not respect user access rights set for data sources in the |
CV1-6063 |
Exporting to an Excel template didn't allow for more than 9 image occurrences. |
CV1-6032 |
Simple search gave an Object reference not set to an instance of object error. |
CV1-6031 |
Choosing a broader term was sometimes not possible; although no circular reference could be found, an error message was generated. |
CV1-6030 |
When users with the 2024-04-29 10:24:10.7906|ERROR|GlobalResources|Axiell.Alm.Services.RecordEditor.Models.ScreenLoadException: An error occurred loading screen copybook. Permission denied to access 'copies'. A simple Error without specification will be shown in Collections. |
CV1-5966 |
A syntax error in More information about this file can be found here. |
CV1-5951 |
Deep links with special characters like |
CV1-5945 |
It was impossible to import CSV data that uses links to non-unique terms / names into fields with an associated domain |
CV1-5941 |
The Merge selected records function did not highlight all source fields that were about to be merged automatically. The fix ensures that they are highlighted and also allows the user to deselect the field by clicking the marked |
CV1-5940 |
It was not possible to import any data into a field of data type |
CV1-5929 |
It was possible to create circular links via ADAPL, for instance via the Change locations task. |
CV1-5920 |
When you hovered the mouse cursor over a field in Edit mode more than five seconds, the field name tooltip would disappear and be replaced by a different, smaller field name tooltip. |
CV1-5912 |
The Copy deep link icon was incorrectly active while creating a new record. |
CV1-5890 |
The Open all panels with data function also opened screens with table grids that had no data in them. |
CV1-5862 |
When the Write set dialogue was open, it was possible to start a new search or open a new record. |
CV1-5851 |
WMTS maps and overlays set up for GeoJSON fields didn't work. The fix (already present in Collections 1.19) requires a new set up in the Maps data source in your application. |
CV1-5795 |
A Simple search on many fields took very long and resulted in an error Execution Timeout Expired... The fix has improved the performance of |
CV1-5772 |
Behind a URL in a Contextual Help text no further text was displayed any more. |
CV1-5762 |
A deleted table grid row seemed to have been definitively removed even when the edited record was not saved, although after switching between records, it turned out the row hadn't been deleted. |
CV1-5754 |
Some checkboxes in dialogues were still displayed in the old design. |
CV1-5676 |
Retrieving metadata worked for many file types, like Note that for a Collections metadata mapping you can only use the metadata properties shown in the ImageMetadataViewer for a loaded file type when you've marked the Axiell Collections meta data only checkbox. |
CV1-5736 |
Two-column sorting in Result set View was lost after opening or closing another view. |
CV1-5434 |
Result set View sorting did not work for several fields even though the blue arrow was present in the column header. Now, when a Linked field points to a multi-field index, Collections tries to find an alternative index to sort on. This alternative index would be the index in the remote database on the tag that is the merge source field for the local Linked field. |
CV1-5418 |
A failure to connect to an IIIF server resulted in a null reference exception, rather than the real error. With the fix (and if the Logging element in 09:09:43.5179|ERROR|GlobalResources|Adlib.Exceptions.TripleIfInformationException: Error receiving iiif information from: http://asfasfdegsdffdsdf/0432fd8fc-1efdab-23fdf-fdca-8bfda89450e.tif/info.json. An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'asfasdjklfasdfasdf' |
CV1-4655 |
A |